How Time Items Work
Time items define when the scheduled settings of a track are checked to determine if a job is required.
The following time items are in use:
- Do Immediately: the default time item on a new track. By default, the tracks are then polled every 10 minutes (600 seconds setting in Attributes). This interval can be adjusted using the polling settings on the Attributes tab. It is possible, and based on campaign design desirable, to configure a different polling interval for every track. The 'Do Immediately' time item will only ever pass a recipient through a track once without them leaving the Track and coming back in as a new instance. Therefore, if someone is processed by a track with ' Do Immediately', they pass to the “bottom” of the track and will never leave. A 'Go To' tool or an Events/Trigger should be used to ensure recipients move on.
- After a Period: uses the polling Attributes, with a default poll every 600 seconds but should be adjusted as required. Depending on how recipients enter the track, it is quite possible that no new audience members will meet the elapsed time criteria, so while there will still be an overhead associated with audience and track population checks, no members may actually be processed. The job is unlikely to take a lot of time to process. The 'After a Period' time item will work from the time that the individual recipient entered the track. Therefore, the period is applied to each recipient on a recipient basis not globally.
- On a Schedule: The scheduling settings of this track are checked by the SQL Jobs Service and that service will determine if a job is required. Since the schedule is specified explicitly, there is no ability to change the polling interval and the UI does not display the tab.
- On a Date: The scheduling criteria of this Track will be checked by the SQL Jobs Service when it runs, to determine if a job is required. Since the schedule is specified explicitly, there is no need to change the polling interval and the UI does not display the tab. This node has no repeatability so any missed dates will simply make this tool redundant.
|
|
